Tool Mentor: Capturing the Results of Identify Requirements for Test and Assessing Risk using TestManagerÖ
Purpose
This tool mentor describes how to use Rational TestManager to capture the results of identifying requirements for test and assessing risk, by inserting, editing, and deleting test requirements.
Related Rational Unified Process activities:
Section "Identify Requirements for Test" of Activity: Plan Test
Section "Assess Risk" of Activity: Plan Test
Overview
This Tool Mentor is applicable when running Microsoft Windows 95/98/NT 4.0.
In the Plan Test activity, you identified what you are going to test. That is, you identified the test requirements - the use cases, functions, features, and characteristics of the application that you will implement and execute tests against. Entering these test requirements into TestManager will enable you to automatically generate Test Coverage reports and track your progress in subsequent test activities.
Perform the following tasks to create a Requirements Hierarchy or to modify an existing one in TestManager:
1. Insert a requirement 
Insert requirements to create a new test requirements hierarchy or to add requirements to an existing hierarchy.
To insert a requirement:
- Click File -> Open Requirements to open the Requirements Hierarchy. TestManager may take a few moments to initialize the Test Requirements Hierarchy.
- When the Requirements Hierarchy window is displayed, click Edit -> Insert Requirement.
- Select a requirement type from the list. For test requirements the type is usually "TCS Test Case Requirement Type".
- In the Text box, type the requirement name.
- Click the Revision tab.
- In the Description box, type a description for this version of the requirement.
- Click the Attributes tab. Then, click in the value column for each attribute row for which you wish to enter a value. Some of the values are free text, while others will provide you with a drop-down list from which to select values.
- When you finish inserting the requirement, click OK.
- Execute these steps for each requirement you add to your hierarchy. Refer to the steps below to Insert a child requirement.
The new requirement appears in the hierarchy.
2. Insert a child requirement
Use child requirements to organize your test requirements into a hierarchy.
To insert a child requirement:
- Start by selecting a parent requirement and click Edit -> Insert Child Requirement, or right-click the parent requirement in the hierarchy and click Insert Child Requirement.
- Select a requirement type from the list. For test requirements the type is usually "TCS Test Case Requirement Type".
- In the Text box, type the requirement name.
- Click the Revision tab.
- In the Description box, type a description for this version of the requirement.
- Click the Attributes tab. Then, click in the value column for each attribute row for which you wish to enter a value. Some of the values are free text, while others will provide you with a drop-down list from which to select values.
- When you finish inserting the requirement, click OK.
- Execute these steps for each child requirement you add to your hierarchy.
The new child requirement appears in the hierarchy.
3. Edit requirement properties
During the life of the project, you will sometimes need to modify the test requirements hierarchy. You will need to add new requirements, modify existing ones, or delete requirements.
To edit or modify a test requirement:
- Click File -> Open Requirements. TestManager may take a few moments to initialize the Test Requirements Hierarchy.
- When the Requirements Hierarchy opens, select the requirement to be modified and click Edit -> Properties. You may also select the requirement with a right-click and then click Properties.
- Click the Revision tab and update the data as needed.
- Click the History button to view the test requirement's history.
- Click the Attributes tab and click in the value column to modify an attribute. Some of the values are free text, while others provide you with a drop-down list.
- Click OK to save the changes.
- Execute these steps for each test requirement to be modified.
4. Deleting test requirements
When you delete a requirement, all of its child requirements are also deleted. Any references to the deleted test requirements in test scripts will be removed.
To delete a test requirement:
- Click File -> Open Requirements, TestManager may take a few moments to initialize the Test Requirements Hierarchy.
- When the Requirements Hierarchy opens, select the requirement to be deleted and click Edit -> Delete. Alternately, you may select the requirement to be deleted with a right-click and then click Delete.
- TestManager will display a dialog box asking if you want to delete this requirement. Click Yes to confirm or No to cancel the delete).
- Repeat these steps for each test requirement to be deleted.
